Diverse network paths with site hardware redundancy for improved availability

ABSTRACT

A system may determine that a first device is available to transfer traffic via a network and that a second device is available to transfer the traffic via the network. A master mode may be enabled on the first device. The master mode, when enabled on the first device while both the first device and the second device are available to transfer the traffic, may cause the first device to advertise dynamic routing information associated with transferring the traffic. A slave mode may be enabled on the second device. The slave mode, when enabled on the second device, may cause the second device to suppress advertisement of virtual router redundancy protocol routing information associated with transferring the traffic. The system may provide, via the first device and the second device, the traffic via a dynamic network path across the network, and in accordance with the dynamic routing information.

BACKGROUND

Dynamic routing describes the ability of a network to alter a networkroute in response to a change in network conditions. As such, dynamicrouting may allow network routes to remain valid in response to thechange in the network conditions.

Virtual Router Redundancy Protocol is a computer networking protocolthat dynamically assigns responsibility for a virtual router to aparticular router of one or more routers (e.g., associated with a localarea network (LAN)). VRRP may provide dynamic fail over of forwardingresponsibility should the particular router become unavailable.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIGS. 3A and 3B are diagrams of example components of one or moredevices of FIG. 2; and

FIG. 4 is a flow chart of an example process for providing traffic via adynamic network path associated with a satellite network, a VRRP networkpath associated with the satellite network, or a path associated with acellular network.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A service provider may operate one or more networks via which a clientsystem (e.g., including one or more devices), associated with a customerof the service provider, may communicate with a remotely located (i.e.,off site) server device. For example, the service provider may operate asatellite network, a cellular network, or the like, that allows theclient system to communicate with a remotely located server device.

In some cases, the satellite network may be capable of supportingmultiple (i.e., different) types of routing protocols associated withtransferring traffic. For example, the satellite network may support adynamic routing protocol (e.g., border gateway protocol (BGP), etc.)capable of transferring the traffic via a dynamic network path withinthe satellite network, a virtual router redundancy protocol (VRRP)capable of transferring the traffic via a VRRP network path within thesatellite network, or the like. However, the dynamic network protocoland the VRRP may operate independently. In other words, the clientsystem may implement the dynamic routing protocol for transfer of thetraffic via the satellite network, or may implement VRRP for transfer ofthe traffic via the satellite network, but may not implement both. Assuch, it may not be possible for a client system to realize the benefitsof both types of network paths. For example, if the client systemimplements the dynamic routing protocol, the client system may notrealize hardware redundancy benefits associated with VRRP. As anotherexample, if the client system implements VRRP, the client system may notbe capable of controlling routing of the traffic as with the dynamicrouting protocol (i.e., routing control may be undertaken by the serviceprovider).

Moreover, if the client system is unable to transfer the traffic via thesatellite network using either the dynamic routing protocol or the VRRP(e.g., when a device included in the satellite network fails), then theclient system may be unable to transfer any traffic.

Implementations described herein provide a client system capable ofusing diverse network paths to transfer traffic via a satellite networkwhile allowing the client system to control routing of the traffic andproviding hardware redundancy. Implementations described herein may alsoallow the client system to transfer the traffic via a cellular networkin the event that the client system is unable to transfer the trafficvia the satellite network.

FIGS. 1A-1C are diagrams of an overview of an example implementation 100described herein. For the purposes of example implementation 100, assumethat a client device is to provide traffic to a remotely located serverdevice via a client system that includes a client edge (CE) device and asatellite device. Further, assume that the client system is capable ofcommunicating with the server device via a satellite network and acellular network. Finally, assume that the satellite network supportsuse of a dynamic routing protocol when routing traffic via the satellitenetwork, and the VRRP when routing traffic via the satellite network.

As shown in FIG. 1A, the client system may receive, from the clientdevice, traffic that is to be provided to the server device. For thepurposes of FIG. 1A, assume that, after receiving the traffic, theclient system determines that both the CE device and the satellitedevice are available to transfer the traffic. As shown, based ondetermining that both the CE device and the satellite device areavailable to transfer the traffic (i.e., that the client system is in anormal operating mode), the client system may cause the CE device toenter a master mode and may cause the satellite device to enter a slavemode. In some implementations, the CE device may be in the master modeas a default (i.e., the client system may not need to cause the CEdevice to enter the master mode). Additionally, or alternatively, thesatellite device may be in the slave mode as a default (i.e., the clientsystem may not need to cause the satellite device to enter the slavemode).

The master mode, when enabled on the CE device while the client systemis in the normal operating mode, may cause the CE device to advertisedynamic routing information, associated with a dynamic routing protocol(e.g., BGP), that allows the traffic to be transferred via a dynamicnetwork path across the satellite network. The slave mode, when enabledon the satellite device, may cause the satellite device to suppressadvertisement of VRRP routing information that may otherwise cause thetraffic to be transferred via a VRRP network path across the satellitenetwork.

As further shown, the client system may provide the traffic to the CEdevice. The CE device may forward the traffic to the satellite deviceand may advertise the dynamic routing information. As shown, thesatellite device may then provide the traffic via the dynamic networkpath across the satellite network in accordance with the dynamic routinginformation. Notably, when the client system is in the normal operatingmode, the satellite device suppresses advertisement of the VRRP routinginformation, which allows the traffic to be provided via the dynamicnetwork path across the satellite network in accordance with the dynamicrouting information provided by the CE device.

Alternatively, as shown in FIG. 1B, the client system may receive, fromthe client device, traffic that is to be provided to the server device.For the purposes of FIG. 1B, assume that, after receiving the traffic,the client system determines that the CE device is not available totransfer the traffic and that the satellite device is available totransfer the traffic. As shown, based on determining that the satellitedevice is available to transfer the traffic and the CE device is notavailable to transfer the traffic, the client system may cause thesatellite device to enter the master mode. The master mode, when enabledon the satellite device, may cause the satellite device to advertise theVRRP routing information that allows the traffic to be transferred viathe VRRP network path across satellite network.

As further shown, the client system may provide the traffic to thesatellite device. The satellite device may advertise the VRRP routinginformation and provide the traffic via the VRRP network path across thesatellite network. In this way, the client system may provide thetraffic via the VRRP network path, associated with the satellitenetwork, when dynamic routing is not possible (i.e., when the CE deviceis not available).

Alternatively, as shown in FIG. 1C, the client system may receive, fromthe client device, traffic that is to be provided to the server device.For the purposes of FIG. 1C, assume that, after receiving the traffic,the client system determines that the CE device is available to transferthe traffic and that the satellite device is not available to transferthe traffic (e.g., that the satellite device is not available and/orthat another device, associated with the satellite network, is notavailable). As shown, based on determining that the CE device isavailable to transfer the traffic and that the satellite device is notavailable to transfer the traffic, the client system may cause the CEdevice to enter the master mode. The master mode, when enabled on the CEdevice when the satellite device is not available to transfer thetraffic (i.e., when only the CE device is available), may cause the CEdevice to set up a cellular network path, across the cellular network,using a mobile routing protocol, such as a dynamic mobile networkrouting (DMNR) protocol (e.g., such that the traffic may be provided viathe cellular network).

As further shown, the client system may provide the traffic to the CEdevice. The CE device may set up the cellular network path using themobile routing protocol, and provide the traffic via the cellularnetwork path across the cellular network. In this way, the client systemmay provide the traffic via the cellular network when dynamic routingand VRRP routing are not possible (e.g., when the satellite deviceand/or another device associated with the satellite network is notavailable).

As indicated above, FIGS. 1A-1C are provided merely as examples. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1C.

In this way, a client system may use diverse network paths to transfertraffic via a satellite network while allowing the client system tocontrol routing of the traffic and providing hardware redundancy.Moreover, in the event that the client system is unable to transfer thetraffic via the satellite network, the client system may transfer thetraffic via a cellular network.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a client device 205, a client system 210that includes a CE device 215 and a satellite device 220, a cellularnetwork 225, a satellite network 230, and a server device 235. Devicesof environment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

Client device 205 may include one or more devices capable of receiving,generating, storing, processing, and/or providing traffic via clientsystem 210. For example, client device 205 may include a communicationand computing device, such as a mobile phone (e.g., a smart phone, aradiotelephone, etc.), a desktop computer, a laptop computer, a tabletcomputer, a handheld computer, a wearable device (e.g., a smart watch),a set-top box, a gaming device, a server, or a similar type of device.In some implementations, client device 205 may receive and/or transmitinformation via client system 210.

Client system 210 may include one or more devices capable of receivingand/or providing traffic destined for and/or provided by client device205 via one or more networks, such as cellular network 225 or satellitenetwork 230. For example, client system may include one or more networkdevices included in a local area network (LAN), such as a switch, arouter, a gateway, a hub, a bridge, a reverse proxy, a server (e.g., aproxy server), a security device, or the like. In some implementations,client system 210 may include client device 205, CE device 215,satellite device 220, and/or one or more other devices.

CE device 215 may include one or more devices capable of processing andtransferring traffic associated with client system 210. For example, CEdevice 215 may include a router, a gateway, a switch, a hub, a bridge, areverse proxy, a server (e.g., a proxy server), or a similar device. Insome implementations, CE device 215 may be capable of implementing adynamic routing protocol such that traffic, associated with clientsystem 210, traverses satellite network 230 via a dynamic network path(e.g., by advertising dynamic routing information associated with thedynamic routing protocol). Additionally, or alternatively, CE device 215may be capable of routing traffic via a cellular network path associatedwith cellular network 225 (e.g., using the DMNR protocol). In someimplementations, CE device 215 may be owned, managed, and/or operated bya customer associated with client system 210.

Satellite device 220 may include one or more devices capable ofprocessing and transferring traffic associated with client system 210.For example, satellite device 220 may include a router, a gateway, aswitch, a hub, a bridge, a reverse proxy, a server (e.g., a proxyserver), or a similar device. In some implementations, satellite device220 may be capable implementing the VRRP such that traffic, associatedwith client system 210, traverses satellite network 230 via a VRRPnetwork path (e.g., by advertising VRRP routing information associatedwith VRRP). In some implementations, satellite device 220 may be owned,managed, and/or operated by the service provider associated withsatellite network 230.

Cellular network 225 may include a cellular network via which traffic,associated with client system 210, may be transferred. For example,cellular network 225 may include a long-term evolution (LTE) network, a3G network, a code division multiple access (CDMA) network, or the like.In some implementations, cellular network 225 may support a mobilerouting protocol for transferring traffic, such as DMNR.

Satellite network 230 may include a satellite network via which trafficmay be transferred. For example, satellite network 230 may be a networkthat supports communication via one or more orbital satellites. In someimplementations, satellite network 230 may include satellite device 220,one or more satellite dishes, one or more orbital satellites, or thelike. In some implementations, satellite network 230 may support adynamic routing protocol (e.g., BGP) for transferring traffic and theVRRP protocol for transferring the traffic.

Server device 235 may include one or more devices associated withsending and/or receiving traffic to and/or from client system 210associated with client device 205. For example, server device 235 mayinclude a server or a group of servers. In some implementations, serverdevice 235 may be capable of communicating with client device 205 viacellular network 225 and/or satellite network 230.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3A is a diagram of example components of a device 300. Device 300may correspond to client system 210, CE device 215, and/or satellitedevice 220. In some implementations, client system 210, CE device 215,and/or satellite device 220 may include one or more devices 300 and/orone or more components of device 300. As shown in FIG. 3A, device 300may include one or more input components 305-1 through 305-A (A≧1)(hereinafter referred to collectively as input components 305, andindividually as input component 305), a switching component 310, one ormore output components 315-1 through 315-B (B≧1) (hereinafter referredto collectively as output components 315, and individually as outputcomponent 315), and a routing component 320.

Input component 305 may include points of attachment for links (e.g.,physical links, wireless links, etc.) and may be points of entry fortraffic, such as packets. Input component 305 may process receivedtraffic, such as by performing data link layer encapsulation ordecapsulation. In some implementations, input component 305 may sendpackets to output component 315 via switching component 310.

Switching component 310 may interconnect input components 305 withoutput components 315. Switching component 310 may be implemented usingone or more of multiple, different techniques. For example, switchingcomponent 310 may be implemented via busses, via crossbars, and/or withshared memories. The shared memories may act as temporary buffers tostore traffic from input components 305 before the traffic is eventuallyscheduled for delivery to output components 315. In someimplementations, switching component 310 may enable input components305, output components 315, and/or routing component 320 to communicate.

Output component 315 may include points of attachment for links (e.g.,wireless links, physical links, etc.) and may be points of exit fortraffic, such as packets. Output component 315 may store packets and mayschedule packets for transmission on output physical links. Outputcomponent 315 may include scheduling algorithms that support prioritiesand guarantees. Output component 315 may support data link layerencapsulation or decapsulation, and/or a variety of higher-levelprotocols. In some implementations, output component 315 may sendpackets and/or receive packets.

Routing component 320 may include one or more processors,microprocessors, field-programmable gate arrays (FPGAs),application-specific integrated circuit (ASICs), or similar types ofprocessing components. In some implementations, routing component 320may communicate with other devices, networks, and/or systems connectedto device 300 to exchange information regarding network topology.Routing component 320 may create routing tables based on the networktopology information, create forwarding tables based on the routingtables, and forward the forwarding tables to input components 305 and/oroutput components 315. Input components 305 and/or output components 315may use the forwarding tables to perform route lookups for incomingpackets.

The number and arrangement of components shown in FIG. 3A are providedas an example. In practice, device 300 may include additionalcomponents, fewer components, different components, or differentlyarranged components than those shown in FIG. 3A. Additionally, oralternatively, a set of components (e.g., one or more components) ofdevice 300 may perform one or more functions described as beingperformed by another set of components of device 300.

FIG. 3B is a diagram of example components of a device 325. Device 325may correspond to client device 205, client system 210, and/or serverdevice 235. In some implementations, client device 205, client system210, and/or server device 235 may include one or more devices 325 and/orone or more components of device 325. As shown in FIG. 3B, device 325may include a bus 330, a processor 335, a memory 340, a storagecomponent 345, an input component 350, an output component 355, and acommunication interface 360.

Bus 330 may include a component that permits communication among thecomponents of device 325. Processor 335 is implemented in hardware,firmware, or a combination of hardware and software. Processor 335 mayinclude a processor (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), an accelerated processing unit (APU), etc.), amicroprocessor, and/or any processing component (e.g., an FPGA, an ASIC,etc.) that interprets and/or executes instructions. In someimplementations, processor 335 may include one or more processors thatare programmed to perform a function. Memory 340 may include a randomaccess memory (RAM), a read only memory (ROM), and/or another type ofdynamic or static storage device (e.g., a flash memory, a magneticmemory, an optical memory, etc.) that stores information and/orinstructions for use by processor 335.

Storage component 345 may store information and/or software related tothe operation and use of device 325. For example, storage component 345may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 350 may include a component that permits device 325 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 350may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 355 may include a component that provides outputinformation from device 325 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 360 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 325 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 360 may permit device 325to receive information from another device and/or provide information toanother device. For example, communication interface 360 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 325 may perform one or more processes described herein. Device325 may perform these processes in response to processor 335 executingsoftware instructions stored by a computer-readable medium, such asmemory 340 and/or storage component 345. A computer-readable medium isdefined herein as a non-transitory memory device. A memory deviceincludes memory space within a single physical storage device or memoryspace spread across multiple physical storage devices.

Software instructions may be read into memory 340 and/or storagecomponent 345 from another computer-readable medium or from anotherdevice via communication interface 360. When executed, softwareinstructions stored in memory 340 and/or storage component 345 may causeprocessor 335 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3B are providedas examples. In practice, device 325 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3B. Additionally, or alternatively,a set of components (e.g., one or more components) of device 325 mayperform one or more functions described as being performed by anotherset of components of device 325.

FIG. 4 is a flow chart of an example process 400 for providing trafficvia a dynamic network path associated with a satellite network, a VRRPnetwork path associated with the satellite network, or a path associatedwith a cellular network. In some implementations, one or more processblocks of FIG. 4 may be performed by client system 210. In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or includingclient system 210, such as client device 205, CE device 215, satellitedevice 220, and/or another device or group of devices of environment200.

As shown in FIG. 4, process 400 may include receiving traffic associatedwith a client device (block 410). For example, client system 210 mayreceive traffic associated with client device 205. In someimplementations, client system 210 may receive the traffic when clientdevice 205 provides the traffic (e.g., automatically, based on userinput, etc.). In some implementations, the traffic may be destined forserver device 235.

As further shown in FIG. 4, process 400 may include determining whethera CE device, associated with the client system, and a satellite device,associated with the client system, are available to transfer the traffic(block 420). For example, client system 210 may determine whether CEdevice 215 and satellite device 220 are available to transfer thetraffic. In some implementations, client system 210 may determinewhether CE device 215 and satellite device 220 are available to transferthe traffic when client system 210 receives the traffic associated withclient device 205. Additionally, or alternatively, client system 210 maydetermine whether CE device 215 and satellite device 220 are availableto transfer the traffic when client system 210 receives informationindicating that client system 210 is to determine whether CE device 215and satellite device 220 are available to transfer the traffic, such asbased on information indicating that client system 210 is toperiodically (e.g., once every minute, once every 30 minutes, etc.)determine whether CE device 215 and satellite device 220 are availableto transfer the traffic.

In some implementations, client system 210 may determine whether CEdevice 215 is available to transfer the traffic based on informationassociated with CE device 215. For example, client system 210 maydetermine whether CE device 215 is available based on information (e.g.,automatically) provided by CE device 215 (e.g., when CE device 215 isconfigured to periodically provide information associated withavailability of CE device 215, such as once every 30 seconds, once everyone minute, once every five minutes, when CE device 215 is configured toprovide updated availability information when CE device 215 experiencesa change in operation state, a failure, an error, etc.). As anotherexample, client system 210 may determine whether CE device 215 isavailable based on a response, provided by CE device 215, to a requestprovided by client system 210 (e.g., when client system 210 requestsinformation associated with availability of CE device 215), or a lack ofa response within a threshold amount of time (e.g., indicating that CEdevice 215 may be powered-off).

In some implementations, client system 210 may determine whether CEdevice 215 is available based on information, associated with theavailability of CE device 215. For example, client system 210 maydetermine whether CE device 215 is available based on informationindicating whether CE device 215 is powered-on, information indicatingwhether CE device 215 is in an operational state, information associatedwith a failure and/or an error experienced by CE device 215, informationassociated with an amount of available resources of CE device 215 (e.g.,processing resources, memory resources, bandwidth, etc.), or the like.Here, client system 210 may determine that CE device 215 is availablewhen CE device 215 is powered-on, is in an operational state, has notexperienced a failure and/or an error, and has sufficient availableresources (e.g., an amount of resources that satisfies a threshold).Conversely, client system 210 may determine that CE device 215 is notavailable when CE device 215 is not powered-on, is not in an operationalstate, has experienced a failure or an error, or does not havesufficient available resources.

In some implementations, client system 210 may determine whethersatellite device 220 is available to transfer the traffic in a mannersimilar to that as described above with regard to CE device 215.

Additionally, or alternatively, client system 210 may determine whethersatellite device 220 is available to transfer the traffic based oninformation associated with satellite network 230. For example, clientsystem 210 may receive information indicating that a device withinsatellite network 230, via which the traffic is to be provided, ispowered-off, is not in an operational state, has experienced a failureand/or an error, is lacking sufficient resources, or the like. Here,client system 210 may determine that satellite device 220 is notavailable to transfer the traffic based on the information associatedwith satellite network 230 (i.e., client system 210 may determine thatsatellite device 220 is not available when the device within satellitenetwork 230 is not available).

In some implementations, client system 210 may determine whethersatellite device 220 is available to transfer the traffic when (e.g.,before, after, concurrently with, etc.) client system 210 determineswhether CE device 215 is available to transfer the traffic.

As further shown in FIG. 4, if both the CE device and the satellitedevice are available to transfer the traffic, then process 400 mayinclude providing the traffic via a dynamic network path associated witha satellite network (block 430). For example, if both CE device 215 andsatellite device 220 are available to transfer the traffic, then clientsystem 210 may provide the traffic via a dynamic network path associatedwith satellite network 230. In some implementations, when client system210 determines that both CE device 215 and satellite device 220 areavailable to transfer the traffic, client system 210 may be described asbeing in a “normal operating mode.”

In some implementations, based on determining that both CE device 215and satellite device 220 are available to transfer the traffic (i.e.,when client system 210 is in the normal operating mode), the dynamicnetwork path, associated with satellite network 230, may be used totransfer the traffic. The dynamic network path may be a network path,associated with a dynamic routing protocol (e.g., BGP), across satellitenetwork 230 via which the traffic may be transferred.

In some implementations, based on determining that both CE device 215and satellite device 220 are available to transfer the traffic, clientsystem 210 may cause CE device 215 to enter a master mode, and may causesatellite device 220 to enter a slave mode. In some implementations, themaster mode may be enabled on CE device 215 as a default (i.e., clientsystem 210 may not need to cause CE device 215 to enter the mastermode). Additionally, or alternatively, the slave mode may be enabled onsatellite device 220 as a default (i.e., client system 210 may not needto cause satellite device 220 to enter the slave mode).

The master mode, when enabled on CE device 215 while client system 210is in the normal operating mode, may cause CE device 215 to advertisedynamic routing information that allows the traffic to be transferredvia the dynamic network path. The slave mode, when enabled on satellitedevice 220, may cause satellite device 220 to suppress advertisement ofVRRP routing information that would cause the traffic to be transferredvia a VRRP network path.

In other words, while in the normal operating mode, CE device 215 mayimplement the dynamic routing protocol in order to dynamically controlrouting of the traffic, while the VRRP may not be used. Here, satellitedevice 220 may be configured with a VRRP/dynamic routing capability thatallows satellite device 220 to support use of both the dynamic networkpath and the VRRP network path, but causes satellite device 220 tosuppress use of the VRRP path when client system 210 is in normaloperating mode (i.e., when satellite device 220 is in the slave mode).

In some implementations, when CE device 215 is in the master mode andsatellite device 220 is in the slave mode, CE device 215 may receive thetraffic from client device 205 and provide the traffic to satellitedevice 220. Here, since satellite device 220 is in the slave mode (e.g.,such that satellite device 220 suppresses advertisement of the VRRProuting information), satellite device 220 may forward the traffic suchthat the traffic travels via the dynamic network path in accordance withthe dynamic routing information advertised by CE device 215. In thisway, client system 210 may provide the traffic via the dynamic networkpath, associated with satellite network 230, when client system 210 isin the normal operating mode. Furthermore, CE device 215 may controlrouting of the traffic even when using dynamic routing over satellite.An example case in which the traffic is provided via the dynamic networkpath is described above with regard to FIG. 1A.

As further shown in FIG. 4, if the CE device is not available totransfer the traffic and the satellite device is available to transferthe traffic, then process 400 may include providing the traffic via aVRRP network path associated with the satellite network (block 440). Forexample, client system 210 may determine that CE device 215 is notavailable to transfer the traffic and that satellite device 220 isavailable to transfer the traffic, and client system 210 may provide thetraffic via the VRRP network path associated with satellite network 230.

In some implementations, based on determining that CE device 215 is notavailable and that satellite device 220 is available (i.e., that onlysatellite device 220 is available), client system 210 may provide thetraffic such that the traffic travels via the VRRP network pathassociated with satellite network 230. The VRRP network path may be anetwork path, associated with VRRP, across satellite network 230 viawhich the traffic may be transferred.

In some implementations, based on determining that only satellite device220 is available to transfer the traffic, client system 210 may causesatellite device 220 to enter the master mode. The master mode, whenenabled on satellite device 220, may cause satellite device 220 toadvertise the VRRP routing information that allows the traffic to betransferred via the VRRP network path associated with satellite network230. In other words, enabling the master mode on satellite device 220may cause satellite device 220 to cease suppressing advertisement of theVRRP routing information. By allowing the VRRP to be implemented whendynamic routing is unavailable, client system 210 may achieve hardwareredundancy. In other words, the traffic may still be provided to serverdevice 235 even when CE device 215 is not available.

In some implementations, when satellite device 220 is in the mastermode, satellite device 220 may receive the traffic from client device205 (e.g., rather than CE device 215 as in the normal operating mode),and may advertise the VRRP routing information and provide the trafficsuch that the traffic travels via the VRRP network path in accordancewith the VRRP routing information. In this way, client system 210 mayprovide the traffic via the VRRP network path, associated with satellitenetwork 230, when only satellite device 220 is available to transfer thetraffic. An example case in which the traffic is provided via the VRRPnetwork path is described above with regard to FIG. 1B.

As further shown in FIG. 4, if the CE device is available to transferthe traffic and the satellite device is not available to transfer thetraffic, then process 400 may include providing the traffic via acellular network path associated with a cellular network (block 450).For example, client system 210 may determine that CE device 215 isavailable to transfer the traffic and that satellite device 220 is notavailable to transfer the traffic, and client system 210 may provide thetraffic via a network path associated with a cellular network.

In some implementations, based on determining that CE device 215 isavailable and that satellite device 220 is not available (i.e., thatonly CE device 215 is available), client system 210 may use the cellularnetwork path, associated with cellular network 225, to transfer thetraffic. The cellular network path may be a network path, associatedwith a mobile routing protocol (e.g., DMNR), across cellular network 225via which the traffic may be transferred.

In some implementations, based on determining that only CE device 215 isavailable to transfer the traffic, client system 210 may cause CE device215 to remain in the master mode. The master mode, when enabled on CEdevice 215 when only CE device 215 is available to transfer the traffic,may cause CE device 215 to set up the cellular network path using themobile routing protocol such that the traffic may be transferred via thecellular network path associated with cellular network 225. In this way,the traffic may be provided to server device 235 even when satellitedevice 220 and/or a device associated with satellite network 230 is notavailable to transfer the traffic.

In some implementations, when only CE device 215 is available and CEdevice 215 is in the master mode, CE device 215 may receive the trafficfrom client device 205, and may set up the cellular network path suchthat the traffic travels via cellular network 225. In this way, clientsystem 210 may provide the traffic via cellular network 225 when only CEdevice 215 is available to transfer the traffic. An example case inwhich the traffic is provided via cellular network 225 is describedabove with regard to FIG. 1C.

In some implementations, when CE device 215 determines that neither CEdevice 215 nor satellite device 220 is available to transfer thetraffic, client system 210 may be unable to provide the traffic. In sucha case, client system 210 may repeat process 400 until client system 210determines that one or both of CE device 215 and satellite device 220are available such that client system 210 may provide the traffic.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

Implementations described herein provide a client system capable ofusing diverse network paths to transfer traffic via a satellite networkwhile allowing the client system to control routing of the traffic andproviding hardware redundancy. Implementations described herein may alsoallow the client system to transfer the traffic via a cellular networkin the event that the client system is unable to transfer the trafficvia the satellite network.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: determining, by a systemand at a first time, that a first device is available to transfertraffic via a network and that a second device is available to transferthe traffic via the network, a master mode being enabled on the firstdevice, the master mode, when enabled on the first device while both thefirst device and the second device are available to transfer thetraffic, causing the first device to advertise first routing informationassociated with transferring the traffic, and a slave mode being enabledon the second device, the slave mode, when enabled on the second device,causing the second device to suppress advertisement of second routinginformation associated with transferring the traffic; and providing, bythe system and via the first device and the second device, the trafficvia a network path across the network, and in accordance with the firstrouting information.
 2. The method of claim 1, where the first routinginformation includes routing information associated with a dynamicrouting protocol, and the second routing information includes routinginformation associated with a virtual router redundancy protocol (VRRP).3. The method of claim 1, further comprising: determining, at a secondtime, that the first device is not available to transfer the traffic viathe network and that the second device is available to transfer thetraffic via the network; causing the second device to enter the mastermode, the master mode, when enabled on the second device, causing thesecond device to advertise the second routing information associatedwith transferring the traffic; and providing, via the second device, thetraffic via another network path across the network and in accordancewith the second routing information.
 4. The method of claim 1, furthercomprising: determining, at a second time, that the first device isavailable to transfer the traffic via the network and that the seconddevice is not available to transfer the traffic via the network, thefirst device remaining in the master mode, the master mode, when enabledon the first device when the second device is not available, causing thefirst device to set up another network path associated with transferringthe traffic via another network; and providing, via the first device,the traffic via the other network path across the other network.
 5. Themethod of claim 4, where the network includes a satellite network andthe other network includes a cellular network.
 6. The method of claim 4,where the other network path is associated with a dynamic mobile networkrouting protocol.
 7. The method of claim 1, further comprising:receiving availability information associated with the first device andavailability information associated with the second device; anddetermining that the first device is available to transfer the trafficvia the network based on the availability information associated withthe first device and that the second device is available to transfer thetraffic via the network based on the availability information associatedwith the second device.
 8. A system, comprising: one or more devices:determine, at a first time, that a first device, of the one or moredevices, is available to transfer traffic via a network and that asecond device, of the one or more devices, is available to transfer thetraffic via the network; enable a master mode on the first device, themaster mode, when enabled on the first device while both the firstdevice and the second device are available to transfer the traffic,causing the first device to advertise dynamic routing informationassociated with transferring the traffic, a slave mode being enabled onthe second device, the slave mode, when enabled on the second device,causing the second device to suppress advertisement of virtual routerredundancy protocol (VRRP) routing information associated withtransferring the traffic; and provide, via the first device and thesecond device, the traffic via a dynamic network path across thenetwork, and in accordance with the dynamic routing information.
 9. Thesystem of claim 8, where the one or more devices are further to:determine, at a second time, that the first device is not available totransfer the traffic via the network and that the second device isavailable to transfer the traffic via the network; enable the mastermode on the second device, the master mode, when enabled on the seconddevice, causing the second device to advertise the VRRP routinginformation associated with transferring the traffic; and provide, viathe second device, the traffic via a VRRP network path across thenetwork and in accordance with the VRRP routing information.
 10. Thesystem of claim 8, where the one or more devices are to: determine, at asecond time, that the first device is available to transfer the trafficvia the network and that the second device is not available to transferthe traffic via the network, the master mode remaining enabled on thefirst device, the master mode, when enabled on the first device when thesecond device is not available, causing the first device to set upanother network path associated with transferring the traffic viaanother network; and provide, via the first device, the traffic via theother network path across the other network.
 11. The system of claim 10,where the network includes a satellite network and the other networkincludes a cellular network.
 12. The system of claim 10, where the othernetwork path is associated with a dynamic mobile network routingprotocol.
 13. The system of claim 8, where the one or more devices arefurther to: receive availability information associated with the firstdevice and availability information associated with the second device;and determine that the first device is available to transfer the trafficvia the network based on the availability information associated withthe first device and that the second device is available to transfer thetraffic via the network based on the availability information associatedwith the second device.
 14. The system of claim 8, where the firstdevice includes a client edge device and the second device includes asatellite device.
 15. A non-transitory computer-readable medium storinginstructions, the instructions comprising: one or more instructionsthat, when executed by one or more processors, cause the one or moreprocessors to: determine, at a first time, that a first device isavailable to transfer traffic via a satellite network and that a seconddevice is available to transfer the traffic via the satellite network;cause the first device to enter a master mode, the master mode, whenenabled on the first device while both the first device and the seconddevice are available to transfer the traffic, causing the first deviceto advertise first routing information associated with transferring thetraffic via the satellite network; cause the second device to enter aslave mode, the slave mode, when enabled on the second device, causingthe second device to suppress advertisement of second routinginformation associated with transferring the traffic via the satellitenetwork; and provide, via the first device and the second device, thetraffic via a network path across the satellite network, and inaccordance with the first routing information.
 16. The non-transitorycomputer-readable medium of claim 15, where the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: determine, at a second time, that thefirst device is not available to transfer the traffic via the satellitenetwork and that the second device is available to transfer the trafficvia the satellite network; cause the second device to enter the mastermode, the master mode, when enabled on the second device, causing thesecond device to advertise the second routing information associatedwith transferring the traffic; and providing, via the second device, thetraffic via another network path across the satellite network and inaccordance with the second routing information.
 17. The non-transitorycomputer-readable medium of claim 16, where the first routinginformation includes routing information associated with a dynamicrouting protocol, and the second routing information includes routinginformation associated with a virtual router redundancy protocol (VRRP).18. The non-transitory computer-readable medium of claim 15, where theone or more instructions, when executed by the one or more processors,further cause the one or more processors to: determine, at a secondtime, that the first device is available to transfer the traffic via thesatellite network and that the second device is not available totransfer the traffic via the satellite network, the first deviceremaining in the master mode, the master mode, when enabled on the firstdevice when the second device is not available, causing the first deviceto set up another network path associated with transferring the trafficvia another network; and providing, via the first device, the trafficvia the other network path across the other network.
 19. Thenon-transitory computer-readable medium of claim 18, where the othernetwork includes a cellular network and the other network path isassociated with a dynamic mobile network routing protocol.
 20. Thenon-transitory computer-readable medium of claim 15, where the one ormore instructions, when executed by the one or more processors, furthercause the one or more processors to: receive availability informationassociated with the first device and availability information associatedwith the second device; and determine that the first device is availableto transfer the traffic via the satellite network based on theavailability information associated with the first device and that thesecond device is available to transfer the traffic via the satellitenetwork based on the availability information associated with the seconddevice.